Shabih Syed
Staff Software Engineer
IBM Lotus Sametime Support
syeds@us.ibm.com

Contributors:
Khalid Abbas
Senior Software Engineer
IBM Lotus Support - Ireland

WARNING: Making changes to registry incorrectly can cause serious problems that may require you to reinstall the OS. IBM cannot guarantee that problems resulting from the incorrect use of registry can be solved. Therefore, always make a backup copy of the registry before making any changes.

Creating Services For Lotus Sametime Systems Console

1. Use a text editor to create a file named CreateServicesSSC.bat and copy/paste the following contents in it.



2. Edit the file CreateServicesSSC.bat using explanations below

Set the paths below to the location of the WebSphere installation. The following path's are the defaults.
cd \Program Files\IBM\WebSphere\AppServer\bin
set PROFILE_PATH=C:\IBM\WebSphere\AppServer\profiles

This section creates the service for Sametime Solution Console's Deployment Manager
In the following section these items need to modified
1. STSCDMgrProfile needs to be replaced with the profile name in your environment. To determine that go under IBM\WebSphere\AppServer\profiles directory
and determine what profile name exists for the Solutions Console's Deployment Manager
2. The wasadmin and sametime fields needs to be replaced with the username and password you created for logging into the Solutions Console during installation
The step for logging into the information center is available here: http://publib.boulder.ibm.com/infocenter/sametime/v8r5/topic/com.ibm.help.sametime.v85.doc/install/inst_config_ssc_login_self.html

wasservice.exe -add ConsoleServerDM -serverName dmgr -profilePath "%PROFILE_PATH%\STSCDMgrProfile" -logRoot "%PROFILE_PATH%\STSCDMgrProfile\logs\dmgr"
wasservice.exe -add "ConsoleServerDM" -servername "dmgr" -profilePath "%PROFILE_PATH%\STSCDMgrProfile" -logRoot "%PROFILE_PATH%\STSCDMgrProfile\logs\dmgr" -stopArgs "-username wasdmin -password sametime" -encodeParams

This section creates the service for Sametime Solution Console's Node
In the following section these items need to modified

1. STSCAppProfile needs to be replaced with the profile name in your environment. To determine that go under IBM\WebSphere\AppServer\profiles directory
and determine what profile name exists for the Solutions Console's Node
2. The wasadmin and sametime fields needs to be replaced with the username and password you created for logging into the Solutions Console during installation

wasservice.exe -add ConsoleServerNodeAgent -serverName nodeagent -profilePath "%PROFILE_PATH%\STSCAppProfile" -logRoot "%PROFILE_PATH%\STSCAppProfile\logs\nodeagent"
wasservice.exe -add "ConsoleServerNodeAgent" -servername "nodeagent" -profilePath "%PROFILE_PATH%\STSCAppProfile" -logRoot "%PROFILE_PATH%\STSCAppProfile\logs\nodeagent" -stopArgs "-username wasadmin -password sametime" -encodeParams

This section creates the service for Sametime Solution Console's Server
In the following section these items need to modified

1. STSCAppProfile needs to be replaced with the profile name in your environment. To determine that go under IBM\WebSphere\AppServer\profiles directory
and determine what profile name exists for the Solutions Console's Server
2. The wasadmin and sametime fields needs to be replaced with the username and password you created for logging into the Solutions Console during installation

wasservice.exe -add ConsoleServerPrimaryNode -serverName STConsoleServer -profilePath "%PROFILE_PATH%\STSCAppProfile" -logRoot "%PROFILE_PATH%\STSCAppProfile\logs\STConsoleServer"
wasservice.exe -add "ConsoleServerPrimaryNode" -servername "STConsoleServer" -profilePath "%PROFILE_PATH%\STSCAppProfile" -logRoot "%PROFILE_PATH%\STSCAppProfile\logs\STConsoleServer" -stopArgs "-username wasadmin -password sametime" -encodeParams

3. Run the CreateServicesSSC.bat by double clicking on it. Verify the new services are created under Windows Services.

Creating Services For Lotus Sametime Proxy

1. Use a text editor to create a file named CreateServicesProxy.bat and copy/paste the following contents in it.



2. Edit the file CreateServicesProxy.bat using explanations below

Set the paths below to the location of the WebSphere installation. The following path's are the defaults.
cd \Program Files\IBM\WebSphere\AppServer\bin
set PROFILE_PATH=C:\IBM\WebSphere\AppServer\profiles

This section creates the service for Sametime Proxy's Deployment Manager
In the following section these items need to modified
1. STPDMgrProfile needs to be replaced with the profile name in your environment. To determine that go under IBM\WebSphere\AppServer\profiles directory
and determine what profile name exists for the Proxy's Deployment Manager
2. The wasadmin and sametime fields needs to be replaced with the username and password you created when you installed the Proxy.

wasservice.exe -add ProxyServerDM -serverName dmgr -profilePath "%PROFILE_PATH%\STPDMgrProfile" -logRoot "%PROFILE_PATH%\STPDMgrProfile\logs\dmgr"
wasservice.exe -add "ProxyServerDM" -servername "dmgr" -profilePath "%PROFILE_PATH%\STPDMgrProfile" -logRoot "%PROFILE_PATH%\STPDMgrProfile\logs\dmgr" -stopArgs "-username wasadmin -password sametime" -encodeParams

This section creates the service for Proxy's Node
In the following section these items need to modified
1. STPAppProfile needs to be replaced with the profile name in your environment. To determine that go under IBM\WebSphere\AppServer\profiles directory
and determine what profile name exists for the Solutions Console's Node
2. The wasadmin and sametime fields needs to be replaced with the username and password you created when you installed the Proxy.

wasservice.exe -add ProxyServerNodeAgent -serverName nodeagent -profilePath "%PROFILE_PATH%\STPAppProfile" -logRoot "%PROFILE_PATH%\STPAppProfile\logs\nodeagent"
wasservice.exe -add "ProxyServerNodeAgent" -serverName nodeagent -profilePath "%PROFILE_PATH%\STPAppProfile" -logRoot "%PROFILE_PATH%\STPAppProfile\logs\nodeagent" -stopArgs "-username wasadmin -password sametime" -encodeParams

This section creates the service for Proxy's Server
In the following section these items need to modified
1. STPAppProfile needs to be replaced with the profile name in your environment. To determine that go under IBM\WebSphere\AppServer\profiles directory
and determine what profile name exists for the Solutions Console's Node
2. The wasadmin and sametime fields needs to be replaced with the username and password you created when you installed the Proxy.

wasservice.exe -add ProxyServerPrimaryNode -serverName STProxyServer -profilePath "%PROFILE_PATH%\STPAppProfile" -logRoot "%PROFILE_PATH%\STPAppProfile\logs\STProxyServer"
wasservice.exe -add "ProxyServerPrimaryNode" -serverName STProxyServer -profilePath "%PROFILE_PATH%\STPAppProfile" -logRoot "%PROFILE_PATH%\STPAppProfile\logs\STProxyServer" -stopArgs "-username wasadmin -password sametime" -encodeParams

3. Run the CreateServiceProxy.bat by double clicking on it. Verify the new services are created under Windows Services.

Creating Services For Lotus Sametime Meeting Server

1. Use a text editor to create a file named CreateServicesMTG.bat and copy/paste the following contents in it.



2. Edit the file CreateServicesMTG.bat using explanations below

Set the paths below to the location of the WebSphere installation. The following path's are the defaults.
cd \Program Files\IBM\WebSphere\AppServer\bin
set PROFILE_PATH=C:\IBM\WebSphere\AppServer\profiles

This section creates the service for Sametime Solution Console's Deployment Manager
In the following section these items need to modified
1. STMDMgrProfile needs to be replaced with the profile name in your environment. To determine that go under IBM\WebSphere\AppServer\profiles directory
and determine what profile name exists for the Solutions Console's Deployment Manager
2. The wasadmin and sametime fields needs to be replaced with the username and password you created when you installed the Meeting Server

wasservice.exe -add MeetingServerDM -serverName dmgr -profilePath "%PROFILE_PATH%\STMDMgrProfile" -logRoot "%PROFILE_PATH%\STMDMgrProfile\logs\dmgr"
wasservice.exe -add "MeetingServerDM" -serverName dmgr -profilePath "%PROFILE_PATH%\STMDMgrProfile" -logRoot "%PROFILE_PATH%\STMDMgrProfile\logs\dmgr" -stopArgs "-username wasdmin -password sametime" -encodeParams

This section creates the service for Meeting Server Node
In the following section these items need to modified

1. STMAppProfile needs to be replaced with the profile name in your environment. To determine that go under IBM\WebSphere\AppServer\profiles directory
and determine what profile name exists for the Solutions Console's Node
2. The wasadmin and sametime fields needs to be replaced with the username and password you created for logging into the Solutions Console during installation

wasservice.exe -add MeetingServerNodeAgent -serverName nodeagent -profilePath "%PROFILE_PATH%\STMAppProfile" -logRoot "%PROFILE_PATH%\STMAppProfile\logs\nodeagent"
wasservice.exe -add "MeetingServerNodeAgent" -serverName nodeagent -profilePath "%PROFILE_PATH%\STMAppProfile" -logRoot "%PROFILE_PATH%\STMAppProfile\logs\nodeagent" -stopArgs "-username wasdmin -password sametime" -encodeParams

This section creates the service for Meeting HTTProxy Server
In the following section these items need to modified

1. STMAppProfile needs to be replaced with the profile name in your environment. To determine that go under IBM\WebSphere\AppServer\profiles directory
and determine what profile name exists for the Solutions Console's Server
2. The wasadmin and sametime fields needs to be replaced with the username and password you created for logging into the Solutions Console during installation

wasservice.exe -add MeetingServerProxy -serverName STMeetingHttpProxy -profilePath "%PROFILE_PATH%\STMAppProfile" -logRoot "%PROFILE_PATH%\STMAppProfile\logs\STMeetingHttpProxy"
wasservice.exe -add "MeetingServerProxy" -serverName STMeetingHttpProxy -profilePath "%PROFILE_PATH%\STMAppProfile" -logRoot "%PROFILE_PATH%\STMAppProfile\logs\STMeetingHttpProxy" -stopArgs "-username wasdmin -password sametime" -encodeParams

This section creates the service for Meeting Server
In the following section these items need to modified

1. STMAppProfile needs to be replaced with the profile name in your environment. To determine that go under IBM\WebSphere\AppServer\profiles directory
and determine what profile name exists for the Solutions Console's Server
2. The wasadmin and sametime fields needs to be replaced with the username and password you created when you installed the Media Server

wasservice.exe -add MeetingServerPrimaryNode -serverName STMeetingServer -profilePath "%PROFILE_PATH%\STMAppProfile" -logRoot "%PROFILE_PATH%\STMAppProfile\logs\STMeetingServer"
wasservice.exe -add "MeetingServerPrimaryNode" -serverName STMeetingServer -profilePath "%PROFILE_PATH%\STMAppProfile" -logRoot "%PROFILE_PATH%\STMAppProfile\logs\STMeetingServer" -stopArgs "-username wasdmin -password sametime" -encodeParams

3. Run the CreateServicesMTG.bat by double clicking on it. Verify the new services are created under Windows Services.

Creating Services For Lotus Sametime Media Server

1. Use a text editor to create a file named CreateServicesMedia.bat and copy/paste the following contents in it.



2. Edit the file CreateServicesMedia.bat using explanations below

This section creates the service for Sametime Media Server Deployment Manager
In the following section these items need to modified
1. STMSDMgrProfile needs to be replaced with the profile name in your environment. To determine that go under IBM\WebSphere\AppServer\profiles directory
and determine what profile name exists for the Solutions Console's Deployment Manager
2. The wasadmin and sametime fields needs to be replaced with the username and password you created for logging into the Solutions Console during installation

wasservice.exe -add MediaServerDM -serverName dmgr -profilePath "%PROFILE_PATH%\STMSDMgrProfile" -logRoot "%PROFILE_PATH%\STMSDMgrProfile\logs\dmgr"
wasservice.exe -add MediaServerDM -serverName dmgr -profilePath "%PROFILE_PATH%\STMSDMgrProfile" -logRoot "%PROFILE_PATH%\STMSDMgrProfile\logs\dmgr" -stopArgs "-username wasdmin -password sametime" -encodeParams

This section creates the service for Media Server Node
In the following section these items need to modified

1. STMSAppProfile needs to be replaced with the profile name in your environment. To determine that go under IBM\WebSphere\AppServer\profiles directory
and determine what profile name exists for the Solutions Console's Node
2. The wasadmin and sametime fields needs to be replaced with the username and password you created for logging into the Solutions Console during installation

wasservice.exe -add MediaServerNodeAgent -serverName nodeagent -profilePath "%PROFILE_PATH%\STMSAppProfile" -logRoot "%PROFILE_PATH%\STMSAppProfile\logs\nodeagent"
wasservice.exe -add MediaServerNodeAgent -serverName nodeagent -profilePath "%PROFILE_PATH%\STMSAppProfile" -logRoot "%PROFILE_PATH%\STMSAppProfile\logs\nodeagent" -stopArgs "-username wasdmin -password sametime" -encodeParams


This section creates the service for Media Server
In the following section these items need to modified

1. STMSAppProfile needs to be replaced with the profile name in your environment. To determine that go under IBM\WebSphere\AppServer\profiles directory
and determine what profile name exists for the Solutions Console's Server
2. The wasadmin and sametime fields needs to be replaced with the username and password you created for logging into the Solutions Console during installation

wasservice.exe -add MediaServerPrimaryNode -serverName STMediaServer -profilePath "%PROFILE_PATH%\STMSAppProfile" -logRoot "%PROFILE_PATH%\STMSAppProfile\logs\STMediaServer"
wasservice.exe -add MediaServerPrimaryNode -serverName STMediaServer -profilePath "%PROFILE_PATH%\STMSAppProfile" -logRoot "%PROFILE_PATH%\STMSAppProfile\logs\STMediaServer" -stopArgs "-username wasdmin -password sametime" -encodeParams

3. Run the CreateServicesMedia.bat by double clicking on it. Verify the new services are created under Windows Services.

Creating Dependencies for Services

1. Use a text editor to create a file named ST85ServiceDependencies.reg and copy/paste the following contents in it.



2. Run the ST85ServiceDependencies.reg by double clicking on it. Verify the dependencies are set by opening the properties of the services

This sets the dependencies for the servers to be on the node agents. The node doesn't need to be dependant on the Deployment manager so that's not included.
Be sure to set all the services to automatic.

Removing a service

To remove the service, run the following command:

WASService -remove "service_name"

Example:
WASService -remove "ConsoleServerDM "

Common Pitfalls

1. Problems with creating the service
When running the script to create the services make sure that the Deployment Manager, Node & Servers are stopped for that component. To verify if any of them are running open the windows task manager and see if any JAVA.exe
processes are listed. If they are then that means you have components in the starting state and you will need to stop them manually otherwise the services will not be created.

2. Problems with Starting/Stopping services
After creating the services verify that you can start and stop the Deployment Manager, Node & Servers. If the service does not start then check to make sure the Profile_Path is correct in the script. Also, in some cases we have discovered that the services do not start if they are set to start with the Local System Account in the service properties. In that case try using a Domain Account and see if it resolves the issue. We have not been able to identify at this point what permission level is causing the issue.

If the service does not stop then that most likely means that you have put invalid credentials in the script. In that case you will need to kill the JAVA.exe process from the task manager, delete the .pid file associated with the process under
for example: IBM/Websphere/appserver/profiles/STSCDMgrProfile/logs/dmgr and then then run the script again.

Note: The script can be run multiple times over for any updates even after you have created the same service. This means that you do not necessarily have to remove the existing service before you can update it for example when you need to update user credentials.